Problem Note 51443: Compressed data sets containing deleted observations that were migrated with PROC MIGRATE might generate errors or cause SAS® to terminate abnormally
Problems can occur when the MIGRATE procedure is used to migrate compressed data sets that contain deleted observations. One of the following error messages might be generated, or your SAS session might stop responding or terminate abnormally, when you attempt to update the migrated data sets using PROC SQL or PROC APPEND:
- ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [SQL (2)]
ERROR: Write Access Violation SQL (2)
Exception occurred at (0345B7E2)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
000000000345B7E2 000000001174E260 sase7:tkvercn1+0x2A7A2
- Error if all avail-space is not in last seg after collect
ERROR: YZR malfunction: file WORK.MS_T_STK_BRK_TDR_MAP_93.DATA trashed or YZR code bug
- SAS WTABORT (SQL (2)) The SAS System has detected an abort condition. An Exception occurred during wthtrm().
Please Contact Technical Support.
|
These errors occur only when migrated, compressed data sets containing deleted observations are updated or a new observation is added, causing SAS to consolidate space in the data set. If no consolidation is done and the observation fits into the existing space, these errors do not occur.
If the data sets were migrated with either PROC COPY or PROC CPORT, this issue does not occur.
If an index is used, first try to re-create the index. In some cases, rebuilding the index is sufficient to remove the error. Otherwise, you need to re-create the data set using the DATA step. Note that observations that are marked for deletion are omitted from the new data set.
Operating System and Release Information
SAS System | Base SAS | Microsoft Windows 2000 Datacenter Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M0 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M0 | |
z/OS | 9.1 TS1M0 | 9.4 TS1M1 |
Microsoft Windows 2000 Server | 9.1 TS1M0 | |
Microsoft Windows 2000 Professional | 9.1 TS1M0 | |
Microsoft Windows NT Workstation | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | |
Microsoft Windows XP Professional | 9.1 TS1M0 | |
64-bit Enabled AIX | 9.1 TS1M0 | 9.4 TS1M1 |
64-bit Enabled HP-UX | 9.1 TS1M0 | 9.4 TS1M1 |
64-bit Enabled Solaris | 9.1 TS1M0 | 9.4 TS1M1 |
HP-UX IPF | 9.1 TS1M0 | 9.4 TS1M1 |
Linux | 9.1 TS1M0 | 9.4 TS1M1 |
OpenVMS Alpha | 9.1 TS1M0 | 9.4 TS1M1 |
Tru64 UNIX | 9.1 TS1M0 | 9.4 TS1M1 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When migrating compressed data sets containing deleted observations and later inserting rows into the data set using PROC SQL or PROC APPEND, you might see errors or your SAS® session might terminate abnormally.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2013-11-04 10:21:18 |
Date Created: | 2013-10-24 17:54:07 |